An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I'm evaluating Foundation Models announced at WWDC 2026 and have a question regarding App Store distribution. My understanding is that Foundation Models are only available on supported devices and operating system versions. For apps that rely on Foundation Models as their primary functionality (rather than offering AI as an optional feature), I'm trying to understand the recommended distribution strategy. Currently, iOS provides Required Device Capabilities to prevent users from installing apps that require hardware features such as GPS, ARKit, or NFC. However, I couldn't find an equivalent Required Device Capability for Foundation Models. I also couldn't find a way to limit App Store availability by supported device models. My questions are: What is the recommended way to distribute an app whose primary functionality depends on Foundation Models? Is there currently any supported mechanism to prevent users with unsupported devices from downloading such an app? Is Apple planning to introduce a Required Device Capability (or a similar App Store filtering mechanism) for Foundation Models before public release? Without such a mechanism, users may be able to install the app successfully but then discover that its primary functionality is unavailable on their device. I'd appreciate any guidance on the recommended approach. Thank you.

Hi everyone, I’m currently experiencing unusually long review waiting times and wanted to ask if others see the same behavior this week. My situation: • App Store update has been in “Waiting for Review” significantly longer than usual • A newly submitted build seems stuck • TestFlight processing is slower than I normally see • Expedited review request and contact attempts didn’t change the status so far What confuses me is that I still see other apps receiving updates, so I’m unsure whether this is a broader review delay or something submission-specific. I’m not trying to escalate anything — just looking to understand if this is currently affecting more developers. Would really appreciate hearing about your recent experiences. Thanks and good luck to everyone waiting 🙂

Hello, Our GAKO Business update has been repeatedly delayed in “Waiting for Review,” despite multiple contacts with Apple Developer Support and an approved expedited review request. App: GAKO Business Version: 1.3.1 Current submission date: July 3, 2026 Current status: Waiting for Review Expedited review: Approved This issue has been ongoing across multiple submissions for approximately one month. We have contacted Apple Developer Support several times and followed up repeatedly under the same support case. However, the current submission has still not entered review. The update contains critical production fixes affecting existing App Store users. GAKO Business is used by real businesses to manage appointments, employees, schedules, services, and customer records. The currently published version contains issues affecting essential business workflows, while the corrected version remains unavailable. Apple has confirmed that the application was placed in the expedited review queue. However, it remains in “Waiting for Review.” We are not asking Apple to bypass the App Review Guidelines. We would like Apple to verify whether the submission is affected by an internal routing issue, technical hold, or another submission-level problem. Has anyone experienced the same situation where expedited review was approved, but the application remained in “Waiting for Review”? If Apple staff sees this post, we would greatly appreciate assistance in checking the submission. Thank you.

Our app has been in review for over a month with no status change or communication from App Review. Typical reviews clear within 24–48 hours, so this is well outside the normal window. Can anyone from App Review advise on next steps or escalate? App details and submission ID available on request. Thanks.

Hi at all,I just published a new version of our application selecting the option "Reset rating when this version is released".The problem is that, even if the application is now available on the apple store the old rating is shown.Any suggestions?Regards,Enzo.

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

Hello, I have a blocking issue in App Store Connect. I need to submit my In-App Purchase together with the app (first-time approval), but: The option to attach In-App Purchases is missing I cannot create a new app version I cannot properly edit the current version This creates a deadlock and prevents me from submitting the app correctly. This does not seem like a configuration issue, but a problem in App Store Connect. Has anyone experienced this or knows how to resolve it? Thank you.

My external TestFlight build for Reverie: Climbing Journal (iOS, build 1.0.0 (7)) was submitted for review on Thursday 2nd July at approximately 00:10 BST. It has now been 5 days with no movement — still showing "Waiting for Review." I have raised 4 support tickets including an expedited review request (case ID 102932291414) and have received no response to any of them. There is no option to get a call back or call and speak to an actual person. A separate app on the same developer account (Get Set) was submitted for external TestFlight review several days later and was approved within 24 hours, so this appears to be specific to this submission rather than a general account issue. I have testers waiting and this is causing significant disruption. Is there anything I can do to progress this, or can anyone from Apple advise on what's happening?

Our application (Apple ID: 6762377822) has been stuck in the Waiting for Review status for more than 5 days. We submitted an expedited review request, but have not yet received a response. We are currently under significant time pressure. We sincerely hope the expedited review request can help facilitate the process and move the review forward as soon as possible. Thank you for your attention and assistance.

Hi everyone, I’m facing an issue with the App Store review / support process and would really appreciate some guidance from others who may have experienced something similar. I have contacted Apple Developer Support multiple times regarding my app, but unfortunately I have not received any meaningful response so far. At this point, I am unsure how to move forward or how to get proper feedback to resolve the issue. The lack of response is making it difficult to proceed with my app submission and address any potential problems on Apple’s side. Has anyone encountered a similar situation? How did you successfully escalate the issue? Is there a specific way to get a response from the review team or developer support? Any advice on how to move forward would be highly appreciated. Thank you in advance!

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hello, My app update has been stuck in the review process for much longer than expected. Here's my current situation: The app update I submitted has been in "Waiting for Review" for longer than the usual 48 hour timeframe, with no progress. I submitted an expedited review request after the 48 hours of submitting but have received no response as of yet. Has anyone else encountered this issue? And what should I do? Thank you.

My app has been stuck in “Waiting for Review” since June 23, 2026. It has now been 10 days without moving to “In Review.” I have already contacted App Review through App Review Status, but I have not received an update yet. I also checked App Store Connect and do not see any missing metadata, Resolution Center messages, App Privacy issues, Age Rating issues, Export Compliance issues, or missing Review Notes. Is anyone else currently experiencing unusually long “Waiting for Review” times? Also, is there anything else I should check on my side before contacting App Review again?

Hello everyone. I hope the Apple team sees my message. I submitted my app for review on June 15th. It's been in the "Waiting for Review" status since then. The app doesn't have any complex structures. No authorization (except for GameCenter), no encryption, etc. It's written in Swift, the native language, and is iOS-exclusive. I've contacted support three times, submitted a request for expedited review, and responded to the emails that arrived confirming my request, but there's been no response, even though the messages indicated a response within 24-48 hours. Apps are successfully submitted to the testing environment. I feel like I'm being ignored. Please help, I'm really looking forward to the App Store release due to the planned events. If anyone has had a similar situation, please share what helped and how long it took for your app to be reviewed, so I can understand how much longer I need to wait.

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

I'm hoping someone here has navigated something similar or can point me to the right channel. My Apple Developer Program membership was terminated, with the notice citing Section 3.2(f) of the ADP Agreement and referring to indications of fraudulent conduct. No specific reason was given. As far as I can tell, the only significant change to my account beforehand was updating my country/region after I relocated. I did this openly through Developer Support: I disclosed the change, Apple asked me to verify my new address, I uploaded a government-accepted document, and a Developer Support agent confirmed Apple had reviewed it and updated my account so I could renew. So the location details on my account are accurate and were verified by Apple itself - which is why the "misrepresentation" framing is confusing to me. Two questions: What is the correct channel to formally appeal or request a review of an account termination? The "file a complaint under a Platform Regulation" link is not available in my region, and the general contact forms do not seem built for this. Has anyone here gone through a 3.2(f) termination and had it reviewed or reversed? What actually worked - phone support, a specific form, persistence? I'm trying to resolve this factually and in good faith. Any guidance is appreciated.

How long the paid apps agreement takes ? im not sure what's going on, I have all active my bank account etc, I added well all the products etc, but still says processing, I ask for help, and no one hasn't answer anything yet, I look on YouTube I didn't find anything, I ask Ai and just says I need to fking wait !! im so tired of waiting desperate also bc I worked so much on this and is crazy that noe apple is taking so much time not sure if this is real or what's going on!!

Hi App Review team, I'm posting here as a last resort after7 weeks with no movement and 4 unanswered support requests. I'm about to lose my launch window next week and I need someone at Apple to look at this. The situation: App: BMH Themes — App ID 6763770421 — Bundle ID com.bringmedinahome.bmhthemes Version 1.0 (Build 24): reviewed and APPROVED, currently "Ready for Distribution". In-app purchases: 904 are APPROVED, but 1,134 have been stuck in "Waiting for Review" for 7 weeks. The 1,134 stuck items are the exact same type as the 904 already approved — so this is clearly not a content issue. None of the 1,134 show any rejection or "Developer Action Needed" message. Nothing is pending on my side. I have submitted 4 support requests over the past weeks. None received a substantive response. Why this is urgent: My company is now legally registered, my VAT number is being issued, my business bank account is active, and my full marketing campaign is finalized for a launch next week. I cannot launch with 1,134 of my products frozen — releasing a half-empty catalog would waste the entire launch. These stuck in-app purchases are the ONLY remaining blocker. My request: Could someone please check whether these 1,134 in-app purchases are correctly queued, confirm whether there is an internal processing issue, and escalate to the App Review / in-app purchase team? The app is already approved — only these items are stuck. Thank you very much for any help.

Hello everyone, I would really appreciate some advice regarding an App Review rejection under Guideline 1.2 because I’m unsure what the best next step is. The review notes included the following statement: “Since this app’s primary functionality is not permitted on the App Store, it would be appropriate to submit a new app with functionality that follows the App Review Guidelines. Resubmitting the app will result in the same or additional App Review Guideline violations.” This wording makes me unsure whether I should submit a new build with the changes I have made or continue discussing the issue through the Resolution Center. The app was rejected because App Review considered its primary purpose to be random or anonymous chat. However, I believe there may have been a misunderstanding about how the application actually works. The application is not a private messaging app, nor is it designed to let people freely chat with strangers. The concept is closer to a discussion that takes place on a user’s profile, similar to two people having a conversation in the comments section of a social media platform. Other authorized users can read those conversations and react to individual messages, so the conversation itself becomes the content rather than functioning as a traditional direct message. Users are never anonymous. Every account has a persistent identity, including a username, profile picture, verified email address, and profile information. The application also includes reporting, blocking, restricting, and moderation features. Communication is intentionally very limited. Users cannot simply message another user whenever they want. Even after all other requirements are met, a user can send only one initial message. The recipient then has 24 hours to decide whether to reply. If the recipient chooses not to reply, the conversation never begins, the thread is automatically moved to the archive after 24 hours, and the sender cannot continue contacting that user. They cannot send another initial message or repeatedly attempt to start a conversation. A conversation can only continue if the recipient voluntarily chooses to reply. Originally, every account was private by default, although users could choose to make their profile public. During App Review, I temporarily made the review accounts public because I wanted the reviewer to be able to explore the application more easily without needing multiple test accounts. Looking back, I now believe this may have unintentionally made the application appear much closer to a stranger chat experience than it was actually designed to be. Another detail that may not have been visible during review is that the reviewer reached the message composition screen but did not actually submit a message. (I saw it on screenshots they attached) If they had submitted it, they would have seen that the initial message does not immediately become an active conversation. Instead, it first enters a pending state where the recipient decides whether to accept it by replying. Without the recipient’s voluntary participation, no conversation is created. After receiving the rejection, I decided to redesign this part of the application to make the communication model even more restrictive. I completely removed the ability for users to have public profiles. Every account is now permanently private. Before any interaction is possible, a user must first send a follow request, and the recipient must explicitly accept that request. Without an accepted follow request, it is impossible to send the initial message. I also removed the discovery feature that could resemble random user discovery and replaced it with standard user recommendation cards similar to those used by many social networking applications. In addition, I implemented follow request rate limiting so users cannot rapidly send large numbers of follow requests. As a result, users can now interact only after mutual consent has already been established through an accepted follow request, and even then, communication is still limited to a single initial message that requires the recipient’s voluntary reply before any conversation can exist. My question is this: Given these changes, would you recommend submitting a new build for review despite the statement that “Resubmitting the app will result in the same or additional App Review Guideline violations,” or would it be better to continue discussing the issue through the Resolution Center first? (Some why they don't reply me at all) If anyone has dealt with a similar Guideline 1.2 situation, I would sincerely appreciate your advice on how you would proceed. Thank you very much for your time

Hi everyone, I’m looking for guidance because I’m struggling to understand an App Review decision. My app, The Leaf Cellar, is a cigar companion app that includes cigar image scanning, humidor management, cigar journals, tasting notes, lounge discovery, and recommendations. My app was rejected, yet there are multiple applications currently on the App Store with substantially similar functionality, including: Ember: AI Cigar Companion (released this year) My Humidor – Cigar Journal Humidor Journal Pro ACJ These apps continue to receive updates and remain available on the App Store. I’m trying to understand what materially distinguishes my implementation from theirs. If Apple considers my app to violate a specific guideline, I would appreciate understanding what objective difference exists between my app and these already approved apps. Has anyone experienced a similar situation where comparable apps were approved but theirs was rejected? Were you able to resolve it through App Review or the App Review Board? Any advice on how to present the strongest case would be greatly appreciated. I’m not looking for speculation or opinions. I’m looking for a clear explanation of how the App Store Review Guidelines are being applied in this case, especially given that a competing app with substantially similar functionality was approved and released this year. From my perspective, the current outcome appears inconsistent, and I would appreciate any insight from developers who have successfully navigated a similar situation. Thank you.